Preparatory slice for P4a (#1478). This introduces no aggregate. No ReplaySessionTransaction, no SessionScriptPublication, no tagged session-script cluster, and no production publication writer is migrated — all of that is the separate P4a PR. This exists so that PR is reviewable.

1. Session-script test factories

~250 direct writes of saveScript*/recordSession were spread across the daemon test tree as inline object literals. P4a proper has to change the shape of every one of them, so they get a name first.

Three factories next to the existing makeIosSession in src/__tests__/test-utils/session-factories.ts:

40 inline session literals across 11 test files now go through them. The heaviest is session-script-writer.test.ts (24 literals, 20+ of which spelled out the same three-to-five-field combination). Named "authoring" rather than "recording" because session.recording is the unrelated screen-capture state, and daemon-runtime-recording-teardown.test.ts already has a local makeRecordingSession meaning that.

The factories write today's fields — pure refactor, no production change, no behavior change, no assertion weakened.

Deliberately left explicit

• session-action-recorder.test.ts / selector-recording.test.ts (9 sites) set saveScriptBoundary: 0 with no recordSession. That is the repair-armed marker in isolation, which is exactly the predicate those tests exercise; forcing them through a factory would add a field production couples but these tests deliberately don't.
• request-router-repair-expired.test.ts's tombstonedSession — a boundary plus repairSourcePath with no recording, one site, no repetition to remove.
• session-store.test.ts keeps its own makeSession: one test mutates session.device.name, and the shared factories hand back the module-level IOS_SIMULATOR by reference, so routing it through them would make that mutation leak across tests. Only the dead-field lines were removed there.
• request-router-typed-error.test.ts keeps its tenant-scoped simulator (simulatorSetPath), now passed into the shared factories as TENANT_SESSION_DEFAULTS rather than re-spelled per test.
• Assertion-only references (session-replay-repair-loop/-empty-tail/-acceptance, the two integration scenarios, request-save-script-transports.test.ts) were left alone — they read the fields, they don't construct them.

2. saveScriptDefaultedHealedPath deleted

Zero production readers, verified. A repo-wide grep finds only three writers (session-replay-runtime.ts:867/870, session-action-recorder.ts:83), the type declaration, the R7 ownership row, and one test assertion. Nothing branches on it: the writer's refuse-on-exist guard (publishHealedScriptAtomically) has been uniform since #1235 — an explicit --save-script=<path> and the default .healed.ad sibling are refused identically — so the flag has been bookkeeping with no consumer.

Deleting it required, in the same commit:

• dropping its row from SESSION_STATE_FIELD_OWNERS in scripts/layering/session-state.ts;
• lowering the R10 baseline in scripts/layering/daemon-modularity.ts: writerOwnedFields 30 -> 29, ownerFileClaims 42 -> 40 (the field claimed two owner files). The ratchet fails on a drop as well as a growth, so this could not be deferred.

scripts/layering/daemon-modularity.test.ts needed no change — it asserts against DAEMON_MODULARITY_BASELINE dynamically rather than against literals. scripts/layering/model.test.ts was checked: its AST fixture string uses saveScriptComplete, not the deleted field, and its field-count assertions derive from the tables, so it is unaffected.

The one test that asserted on the flag (session-script-writer.test.ts) kept its other concern — that close --save-script=<explicit path> re-points a defaulted-healed repair and publishes cleanly to the new target — and lost only the marker assertion.

Gates

pnpm check:layering
Layering guard: OK — ... all 40 SessionState fields are classified and every write is
inside its declared owner (R7); ... R10 pins R7 at 29 writer-owned fields / 40 owner
claims, ...

pnpm check:affected --base origin/main --run: format, lint, typecheck, layering, fallow, mcp-metadata and build all pass. vitest-related runs 236 files / 2269 tests with 1 pre-existing failure: src/daemon/handlers/__tests__/session-test-runner.test.ts ("test dispatches per-platform scripts", ['ios','android'] vs ['android','ios']). It reproduces unchanged on origin/main (32b9db2d7) with this branch stashed, is in the P3 worker's session-test*.ts territory, and is pulled into the related set only because this PR touches src/daemon/types.ts. Every test this PR actually edits passes.

Coordination

The only shared-file edit is the two-line writerOwnedFields/ownerFileClaims baseline in scripts/layering/daemon-modularity.ts — localized, well away from the R10 logical-module policies the P3 worker is editing. session-replay-runtime.ts is touched only at ~867 (the arming step), disjoint from P3's ~461.

Refs #1478

🤖 Generated with Claude Code

https://claude.ai/code/session_01RXQLYV7etZx3gcXsUsrQJ8

Generated by Claude Code